Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge master to master-vs-deps #51352

Merged
18 commits merged into from
Feb 20, 2021
Merged

Conversation

dotnet-bot
Copy link
Collaborator

This is an automatically generated pull request from master into master-vs-deps.

Once all conflicts are resolved and all the tests pass, you are free to merge the pull request. 🐯

Troubleshooting conflicts

Identify authors of changes which introduced merge conflicts

Scroll to the bottom, then for each file containing conflicts copy its path into the following searches:

Usually the most recent change to a file between the two branches is considered to have introduced the conflicts, but sometimes it will be necessary to look for the conflicting lines and check the blame in each branch. Generally the author whose change introduced the conflicts should pull down this PR, fix the conflicts locally, then push up a commit resolving the conflicts.

Resolve merge conflicts using your local repo

Sometimes merge conflicts may be present on GitHub but merging locally will work without conflicts. This is due to differences between the merge algorithm used in local git versus the one used by GitHub.

git fetch --all
git checkout merges/master-to-master-vs-deps
git reset --hard upstream/master-vs-deps
git merge upstream/master
# Fix merge conflicts
git commit
git push upstream merges/master-to-master-vs-deps --force

sharwell and others added 16 commits February 16, 2021 09:23
The `ErrorOutput` field is not used in the compiler protocol because the
compiler never writes to stderr. This was complicating the code path for
no good reason and hence I decided to remove it.
Refactor a bit and clean up some comments to help make the flow of data
a bit clearer here.
This change adds structured messages to the binlog about the behavior of
the compiler server. These messages will help users, our own developers
and automation understand the behavior of the compiler server within a
build.
Avoid capture allocation in AnalyzerFileReference.GetSupportedLanguages
Handle failed SaveAsync operations
Provide structured information in binlog for the compiler server
…expressions (#51213)

Co-authored-by: CyrusNajmabadi <[email protected]>
Co-authored-by: Bernd Baumanns <[email protected]>
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approval

@dotnet-bot dotnet-bot requested a review from a team as a code owner February 20, 2021 17:16
@ghost ghost merged commit 528dad5 into master-vs-deps Feb 20, 2021
@ghost ghost deleted the merges/master-to-master-vs-deps branch February 20, 2021 18:39
@ghost ghost added this to the Next milestone Feb 20, 2021
@allisonchou allisonchou modified the milestones: Next, 16.10.P2 Mar 29, 2021
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants